Appendix H to GM 21.A.101 Examples of documenting the proposed certification basis list    

CAA ORS9 Decision No. 1

H.1 Example 1.

    H.1.1 This optional tool may be used to establish the applicable airworthiness and OSD certification specifications that will become part of the type-certification basis for airworthiness or OSD certification basis. For a significant change, the applicant must demonstrate compliance for the change and the area affected by the change with the certification specifications that were in effect at the date of application. However, in some cases earlier or later certification specifications can be used, as allowed in point 21.A.101.

    H.1.2 In order to efficiently determine and agree upon a certification basis with the CAA, the following information is useful to understand the applicant’s position:

      H.1.2.1 The scope of the change. This includes a high-level description of the physical and functional changes and performance/functional characteristics, which are changed as a result of the physical or functional change, and the certification specifications for which compliance demonstration is required as a result of the change.

      H.1.2.2 The amendment level of all the applicable certification specifications at the date of application.

      H.1.2.3 The proposed certification basis, including amendment levels.

      H.1.2.4 Applicants who propose a certification basis that includes amendment levels earlier than what was in effect at the date of application should include the exception as outlined in point 21.A.101 and their justification if needed.

    H.1.3 Exceptions.

      H.1.3.1 Unrelated changes that are not significant (point 21.A.101(b)(1)).

      H.1.3.2 Not affected by the change (point 21.A.101(b)(2)).

      H.1.3.3 Compliance with the certification specification would not contribute materially to the level of safety (point 21.A.101(b)(3)).

      H.1.3.4 Compliance with the certification specification would be impractical (point 21.A.101(b)(3)).

    H.1.4 One easy way to document the proposed certification basis is using a tabular form as shown in Table below.

Table H-1. Tabular Form for Documenting a Proposed Certification Basis
CS Amendment Levels

Applicant Justification for Lower Amendment Level and Comments

Affected Area

Existing TCDS Amendment

Amendment at Date of Application

Proposed Amendment Level
Subpart A — General
           
Subpart B — Flight
           

    H.1.5 Best Practices.

      H.1.5.1 Account for all certification specifications, even if they are not applicable.

      H.1.5.2 Mark certification specifications that are not applicable as ‘N/A’.

      H.1.5.3 If more than one amendment level is used depending on the area of the product, list all areas and amendment levels at each area with proper justification.

      H.1.5.4 If the justification is long, provide the justification below the table and only place the certification specification reference and note in the comment field.

      H.1.5.5 Include airworthiness and OSD standards required by other regulations (e.g. Part-26) of affected areas.

      H.2    Example 2.

The following pages of this Appendix contain another example for documenting a proposed certification basis.

 

 

 

 

 

 

 

 

 

 

TITLE OF DESIGN CHANGE

Product Name or Change to Type Certificate [XXXX]

Proposed Certification Basis Pursuant to point 21.A.101